home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
10_7_06.tro
< prev
next >
Wrap
Text File
|
1991-12-12
|
26KB
|
1,360 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright ( c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v | 5i'
.sp 2P
.LP
\fBRecommendation\ Z.336\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBTRAFFIC\ MEASUREMENT\ ADMINISTRATION\fR
.EF '% Fascicle\ X.7\ \(em\ Rec.\ Z.336''
.OF '''Fascicle\ X.7\ \(em\ Rec.\ Z.336 %'
.ce 0
.sp 1P
.LP
\fR \fB1\fR \fBGeneral\fR
.sp 1P
.RT
.PP
This Recommendation has been developed in accordance to the
methodology defined in Recommendations\ Z.332 and\ Z.333.
.PP
The main part of this Recommendation deals with the model of Traffic Measurement
Administration and a glossary of the terms used is also included.
.PP
The list of operator jobs and the list of system functions to be
controlled are contained in Annex\ A.
.PP
For each system function to be controlled by means of MML, one or more
MML functions can be derived and each of them can be described using the
metalanguage defined in Recommendation\ Z.333, in order to detail the relevant
information structure.
.PP
Annex B contains a list of MML functions and information structure
diagrams associated to each of them to be used as guidelines.
.RT
.sp 2P
.LP
\fB2\fR \fBIntroduction\fR
.sp 1P
.RT
.PP
Traffic measurement administration functions are related to
data production, collection and output.
.PP
These data are achieved by means of periodic and non\(hyperiodic
traffic measurements carried out in the telecommunications systems and are
output by the systems in a suitable form.
.PP
The traffic measurement result outputs should contain the measurement results
and general information about the measurement itself and about the
system which performed the measurement, in order to ease the results analysis.
Moreover, they should contain information summarizing the production of
output blocks for checking purposes.
.PP
The traffic measurement model in \(sc\ 4 is based upon a more
general measurement model given in \(sc\ 3.
.RT
.sp 2P
.LP
\fB3\fR \fBGeneral measurement model\fR
.sp 1P
.RT
.PP
A measurement is identified by three basic elements: time,
entities, objects.
.PP
Time includes all the necessary information to define the start,
the duration and periodicity of a certain measurement.
.PP
Entities describe the quantities for which data collection must be
performed with a certain measurement, e.g.\ traffic flow, number of call
attempts, congestion time.
.PP
Objects are intended as individual items within each object type on
which the measurements are performed. Examples of object types are subscriber
lines, circuits, circuit groups, elements of switching networks, geographical
areas with their corresponding dialled code. The definition of measurements
is based on an abstract model which contains the definition of a measurement
matrix (see Figure\ 1/Z.336) in which each row represents one uniquely
definable entity, e.g.\ number of call attempts, and each column represents
a uniquely
definable object type, e.g. incoming junction group (see Figure\ 2/Z.336).
.RT
.PP
A certain combination of entities and object types corresponds to certain
entries in the measurement matrix and forms a measurement type. It is recognized
that part of these measurement types may be standardized while the rest
of them seem to be system and/or administration dependent. It should be
noted that some of the entries in the measurement matrix could be impossible
(e.g.\ call congestion on an incoming trunk) and some others could be more or
less meaningless. A single object is defined by its type and/or its individual
object identity. In some measurement types, the number of objects is fixed.
In other types, one can choose for the actual measurement some or all of
the
allowed objects by means of MML commands. The chosen (selected) objects
form an object list.
.PP
The structure of the division of object types and entities is
open\(hyended, in such a way that any new object type or entity may be
added.
.bp
.RT
.LP
.rs
.sp 18P
.ad r
\fBFigure 1/Z.336, p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 17P
.ad r
\fBFigure 2/Z.336, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
\fB4\fR \fBTraffic measurement administration model\fR
.sp 1P
.RT
.sp 1P
.LP
4.1
\fIBasic classes of measurements\fR
.sp 9p
.RT
.PP
Two basic classes of measurements are envisaged (see
Figure\ 3/Z.336). The first class (A) is measurement of undetermined duration
while the second one (B) is intended to be performed only for a predetermined
duration. The start of a measurement may be intended as instantaneous or
delayed for a defined time duration, \fIt\fR\d1\u, from the activation of the
measurement. Since the stop time of a measurement of class\ A is not given
when the measurement is activated or created, it has to be given during
the
measurement unless the measurement is intended to go on forever.
.bp
.RT
.LP
.rs
.sp 25P
.ad r
\fBFigure 3/Z.336, p.\fR
.sp 1P
.RT
.ad b
.RT
.PP
From the deactivation point of time there may be a defined delay of \fIt\fR\d2\ubefore
the measurement is stopped. In the creation of a measurement a start time
may optionally be provided, in which case for that particular
measurement, the activation function is not necessary.
.PP
Time parameters needed to control a measurement can be divided into
three groups:
.RT
.LP
1)
measurement type dependent time parameters [interval
parameters of a measurement type, e.g.\ sampling
interval
.FS
Sampling interval, the time interval between
two consecutive samplings.
.FE
];
.LP
2)
measurement dependent time parameters (e.g.\ time parameters
which define the periodicity of measurement);
.LP
3)
measurement independent time parameters (e.g.\ time
parameters which are related to the actual start or stop of a
certain measurement in activation and deactivation
functions).
.sp 1P
.LP
4.2
\fITraffic measurement structure\fR
.sp 9p
.RT
.PP
A traffic measurement (in the following called measurement)
consists of:
.RT
.LP
\(em
measurement set information,
.LP
\(em
time information,
.LP
\(em
output routing and scheduling information (output
parameters).
.PP
Measurement set information, time information, output routing
and scheduling information may be completely or partially pre\(hydefined
(initially provided by the supplier but changeable via MML inputs) or fixed
(not changeable via MML inputs). The MML functions described for traffic
measurements administration are intended to be supported to the extent that
there is a need for user manipulation of the identified information
items.
.PP
If some of this information is fixed in a system, the relevant
MML functions may not be provided in that system.
.RT
.LP
.sp 1
.bp
.sp 1P
.LP
4.2.1
\fIMeasurement set information\fR
.sp 9p
.RT
.PP
Measurement set information consists of one or several selected
measurement types with defined objects (object lists) and measurement type
dependent parameters (e.g.\ sampling interval, number of events of a certain
category, destination codes,\ etc.).
.PP
Note that for traffic measurement administration purposes measurement types
are fixed at a given moment in time and they cannot be created, deleted
or changed by MML commands; these measurement types may be changed only
later by supplier releases according to new requirements. It is recognized
that
administrations may require MML functions to administer measurement types,
grouping predefined entities of object types. Such functions should be
considered as system extension and upgrade functions and, therefore, they
should belong to the system control functional area. However, due to the
fact that system control functions will not be inserted in the present
Recommendations, they are described hereafter.
.RT
.sp 1P
.LP
4.2.2
\fITime information\fR
.sp 9p
.RT
.PP
Measurements of types A and B may involve continuous recording or recording
on predetermined days (recording days).
.PP
For measurements performing continuous recording only the start data is
needed.
.PP
For recording on predetermined days, these days are determined on a
periodical basis (periodicity pattern) in case of measurements of undetermined
duration. For measurements of predetermined duration, the recording days
are
determined on a periodical basis or on a non\(hyperiodical basis (dates of
recording days). These possibilities are summarized in Figure\ 4/Z.336.
.RT
.LP
.rs
.sp 15P
.ad r
\fBFigure 4/Z.336, p.\fR
.sp 1P
.RT
.ad b
.RT
.PP
Time data are defined at three main levels, as shown in
Figure\ 5/Z.336.
.PP
\fIMeasurement level\fR | ontains information about either:
.RT
.LP
\(em
dates of recording days (in case of a non\(hyperiodical
measurement). The start and stop date of the measurement are
implicitly defined by the dates of the first and the last
recording day. No activation function may be needed in this
case;
.LP
\(em
periodicity pattern (in case of periodical measurement) of
recording and non\(hyrecording days.
.PP
\fIRecording day level\fR | ontains information about the start time and
stop time for the recording periods within a recording day (e.g.\ from
09
to\ 12 and from\ 15 to\ 17). No overlap of recording periods is allowed for the
same measurement.
.PP
\fIRecording period level\fR | ontains information about the periodicity
of the data collection based on the result accumulation period. The result
accumulation period is the time interval within a recording period during
which the required measurement entities are processed and at the end of
which results are stored for immediate or later output (e.g.\ 15\ minutes).
The result
.PP
accumulation period can be shorter than the recording period; in that case
more than one set of data is collected for each of the recording periods
to be
routed toward the output media according to the results output
schedule.
.bp
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure 5/Z.336, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
\fB5\fR \fBAdditional information\fR
.sp 1P
.RT
.sp 1P
.LP
5.1
\fIMeasurement output contents and procedures\fR
.sp 9p
.RT
.PP
Activation of a traffic measurement causes the output of
measurement results with the following procedures.
.PP
The produced output is routed toward the media specified in the
output routing list associated to the measurement, e.g.\ printers, magnetic
tapes, data links, system output files,\ etc. The output is made according
to the output schedule.
.PP
The measurement results output is done according to time data related to
the measurement. A measurement results output is made with the following
logical blocks:
.RT
.LP
a)
a \*Qbegin block\*U which contains measurement data, parameters
i.e.\ measurement types data, time data, output data and data of
interest related to the exchange configuration;
.LP
b)
one or more \*Qresult blocks\*U, one for each result output
period, which contain the measurement results;
.LP
c)
an \*Qend block\*U which contains a general summary about the
performance of the measurement, i.e.\ number of result blocks,
number of interruptions of the measurement and the causes of the
deactivation of the measurement (scheduled or forced).
.PP
If during the performance of the measurement, the measurement is suspended
(e.g.\ due to a system crash) the measurement results output could be continued
after the system restart with a new output of the begin block. This continuation
may be accomplished automatically by the system or by user action. The
system should notify the user via an output if the latter case applies.
.PP
The relationship between time data for the result accumulation period and
time data defining the results output schedule is system or even
measurement dependent and it is not considered herein.
.bp
.RT
.sp 1P
.LP
5.2
\fISimplification of traffic measurement administration\fR
.sp 9p
.RT
.PP
It is recognized that, for particular applications, there may not be an
interest in administering the data base of traffic measurements.
Consequently, the only MML functions needed are activation and deactivation
functions.
.PP
In such cases, in order to ease the operator's work, the association between
the measurement and the objects may be made when activating the
measurement itself, provided that the association is unambiguous.
.RT
.sp 2P
.LP
\fB6\fR \fBGlossary of used terms\fR
.sp 1P
.RT
.sp 1P
.LP
\fBRecording\fR
.sp 9p
.RT
.PP
Performance of the operations implied by the measurement entities in order
to collect the required data.
.RT
.sp 1P
.LP
\fBrecording day\fR
.sp 9p
.RT
.PP
Day when a recording is performed. Several recording periods are allowed
within a recording day. No overlap of recording periods is allowed for
the same measurement. Each recording period can have a different length.
.RT
.sp 1P
.LP
\fBstart date\fR
.sp 9p
.RT
.PP
Start day for the measurement execution.
.RT
.sp 1P
.LP
\fBstop date\fR
.sp 9p
.RT
.PP
Stop day for the measurement execution.
.RT
.sp 1P
.LP
\fBperiodicity pattern\fR
.sp 9p
.RT
.PP
A pattern which indicates which days are recording (or results
output) days and which are not. The start day positions this time span. Once
activated, the execution of the measurements (or of the results output) is
performed according to this pattern, until disabled by a deactivation
command.
.RT
.sp 1P
.LP
\fBstart time\fR
.sp 9p
.RT
.PP
Time for beginning the recording period in a recording day.
.RT
.sp 1P
.LP
\fBstop time\fR
.sp 9p
.RT
.PP
Time for terminating a recording period in a recording day.
.RT
.sp 1P
.LP
\fBrecording period\fR
.sp 9p
.RT
.PP
A period of recording during a recording day.
.RT
.sp 1P
.LP
\fBresults accumulation period\fR
.sp 9p
.RT
.PP
Time interval within a recording period during which the required measurement
entities are processed and at the end of which results are stored for immediate
or later output.
.RT
.sp 1P
.LP
\fBoutput parameters\fR
.sp 9p
.RT
.PP
Data determining output routing and scheduling.
.RT
.sp 1P
.LP
\fBresults output routing\fR
.sp 9p
.RT
.PP
Data defining the media to which results output is to be
directed.
.RT
.sp 1P
.LP
\fBresults output schedule\fR
.sp 9p
.RT
.PP
Data specifying a set of days (or a periodicity pattern) and of
times during these days when the output of the results is to be
made.
.bp
.RT
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation Z.336)
.sp 9p
.RT
.ce 0
.ce 1000
\fBList of system functions to be controlled by MML and list of jobs\fR
.sp 1P
.RT
.ce 0
.LP
A.1
\fIList of system functions to be controlled by MML\fR
.sp 1P
.RT
.LP
1)
Performing traffic measurements.
.LP
2)
Scheduling traffic measurements execution and results
output.
.LP
3)
Managing measurements' data.
.LP
4)
Retrieving measurements' data.
.sp 1P
.LP
A.2
\fIList of jobs\fR
.sp 9p
.RT
.LP
1)
To create new measurements or measurement components and to
modify old ones, by defining the entities to be measured and the
objects and parameters of the measurements themselves (what and
how to measure):
.LP
\(em
the purpose of this job is to create and/or modify a
set of data which is used by the system to perform a
measurement in a given way;
.LP
\(em
the system is supposed to record the set of data of the
measurement, and to check their static correctness;
.LP
\(em
the user is supposed to input/change all relevant data.
The modification of data may be performed by means of
different procedures, depending whether or not those data
are related to activated measurements;
.LP
\(em
the complexity of the job could be high depending on
the amount of data to be input;
.LP
\(em
the frequency of the job is low;
.LP
\(em
the job is supposed to be performed at exchange and/or
OMC level.
.LP
2)
To delete obsolete measurements or measurement
components:
.LP
\(em
the purpose of the job is to delete measurement of no
further use or measurement components to release the
employed resources;
.LP
\(em
the system is supposed to delete the data related to a
specified measurement if the measurement is not active.
The system is supposed to delete a measurement component
only if it is not an active measurement component;
.LP
\(em
the user is supposed to input the identities of
measurements or measurement components to be deleted;
.LP
\(em
the complexity of the job is low;
.LP
\(em
the frequency of the job is low;
.LP
\(em
the job is supposed to be performed at exchange and/or
OMC level;
.LP
3)
To define the measurement results output routing and
scheduling (where and when the results will be output):
.LP
\(em
the purpose of the job is to define where the
measurement outputs have to be routed to and when they
should be output;
.LP
\(em
the system has to route the measurement outputs toward
the recording media or toward other systems specified,
according to the results output schedule;
.LP
\(em
the user has to input the identity of the
destination of the output and the results output schedule
to be followed by the system;
.LP
\(em
the complexity of the job is low;
.LP
\(em
the frequency of the job is medium;
.LP
\(em
the job may be performed at exchange and/or OMC
level.
.LP
4)
To activate and to deactivate measurements (when to
measure):
.LP
\(em
the purpose of the job is to activate and/or
deactivate the performance of the measurements that have
been previously defined;
.LP
\(em
the system is supposed to activate and/or deactivate a
measurement and to start the production of the results;
.LP
\(em
the user is supposed to input the date and time of
activation and/or deactivation;
.LP
\(em
the complexity of the job is low;
.LP
\(em
the frequency of the job is medium;
.LP
\(em
the job may be performed at exchange and/or OMC
level.
.bp
.LP
5)
To retrieve different kinds of information related to
traffic measurements:
.LP
\(em
the purpose of the job is to get information on
measurements previously input in the system(s) in order to
be aware of the current situation;
.LP
\(em
the system is supposed to output in suitable formats
and on the selected device(s) the information requested;
.LP
\(em
the user is supposed to input the identity of the
items to be interrogated and to select retrieving
criteria;
.LP
\(em
the complexity of the job is low;
.LP
\(em
the frequency of the job is medium;
.LP
\(em
the job may be performed at exchange and/or OMC
level.
\v'1P'
.ce 1000
ANNEX\ B
.ce 0
.ce 1000
(to Recommendation Z.336)
.sp 9p
.RT
.ce 0
.ce 1000
\fBGuidelines for the list of MML functions\fR
.sp 1P
.RT
.ce 0
.ce 1000
\fBand associated information structure diagrams\fR
.ce 0
.LP
B.1
\fIIntroduction\fR
.sp 1P
.RT
.PP
This Annex contains guidelines for the list of MML functions and
associated information structure diagrams related to the routing administration
model defined in Recommendation\ Z.336, \(sc\ 4.
.RT
.sp 1P
.LP
B.2
\fIList of MML functions\fR
.sp 9p
.RT
.PP
This list contains possible MML functions for traffic measurement administration.
Those functions dealing with information (e.g.\ measurement set, time data
list,\ etc.) that is fixed in a system are not relevant for that
system.
.PP
This list is not mandatory nor complete, it may vary according to
Administration needs, telecommunication network levels, regulatory needs,\ etc.
.PP
These MML functions do not represent the actual command structure of any
real implementation of the man\(hymachine interface. Each of the MML functions
identified can be implemented by providing one or more separate distinctive
commands or several MML functions could be implemented by using a single
command.
.RT
.LP
1)
\fICreation\fR
.LP
\(em
create a measurement;
.LP
\(em
create a measurement set;
.LP
\(em
create an object list;
.LP
\(em
create a time data list;
.LP
\(em
create an output routing list;
.LP
\(em
create a result output schedule.
.LP
2)
\fIDeletion\fR
.LP
\(em
delete a measurement;
.LP
\(em
delete a measurement set;
.LP
\(em
delete an object list;
.LP
\(em
delete a time data list;
.LP
\(em
delete an output routing list;
.LP
\(em
delete a result output schedule.
.LP
3)
\fIActivation\fR
.LP
\(em
activate a measurement.
.LP
4)
\fIDeactivation\fR
.LP
\(em
deactivate a measurement.
.bp
.LP
5)
\fIInterrogation\fR
.LP
\(em
interrogate a measurement;
.LP
\(em
interrogate a measurement set;
.LP
\(em
interrogate a mesurement type;
.LP
\(em
interrogate an object list;
.LP
\(em
interrogate a time data list;
.LP
\(em
interrogate an output routing list;
.LP
\(em
interrogate a result output schedule.
.LP
6)
\fIChanging\fR
.LP
\(em
change a measurement;
.LP
\(em
change a measurement set;
.LP
\(em
change an object list;
.LP
\(em
change a time data list;
.LP
\(em
change an output routing list;
.LP
\(em
change a result output schedule.
.LP
7)
\fIAdministration of measurement types\fR
.LP
\(em
create a measurement type;
.LP
\(em
delete a measurement type;
.LP
\(em
change a measurement type.
.sp 1P
.LP
B.3
\fIInformation structure diagrams\fR
.sp 9p
.RT
.PP
The information entities needed for the MML functions previously
defined have been identified and are reported in this section by means of
diagrams representing each MML function information structure (Figures from
B\(hy2/Z.336 to\ B\(hy41/Z.336). In particular, the information structure
diagrams of the measurement outputs are given in Figures from B\(hy42/Z.336
to
B\(hy45/Z.336.
.PP
An overview of the measurement data structure is also given in
Figure\ B\(hy1/Z.336.
.PP
The metalanguage used is defined in Recommendation\ Z.333.
.RT
.LP
.rs
.sp 25P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy1/Z.336, p.6\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy2/Z.336, p.7\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy3/Z.336, p.8\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 32P
.ad r
\fBFigure B\(hy4/Z.336, p.9\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 17P
.ad r
\fBFigure B\(hy5/Z.336, p.10\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy6/Z.336, p.20\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 18P
.ad r
\fBFigure B\(hy7/Z.336, p.21\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 23P
.ad r
\fBFigure B\(hy8/Z.336, p.22\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy9/Z.336, p.23\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 20P
.ad r
\fBFigure B\(hy10/Z.336, p.24\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure B\(hy11/Z.336, p.25\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 13P
.ad r
\fBFigure B\(hy12/Z.336, p.26\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure B\(hy13/Z.336, p.27\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure B\(hy14/Z.336, p.28\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 13P
.ad r
\fBFigure B\(hy15/Z.336, p.29\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure B\(hy16/Z.336, p.30\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure B\(hy17/Z.336, p.31\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 38P
.ad r
\fBFigure B\(hy18/Z.336, p.32\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 11P
.ad r
\fBFigure B\(hy19/Z.336, p.33\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 26P
.ad r
\fBFigure B\(hy20/Z.336, p.34\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 19P
.ad r
\fBFigure B\(hy21/Z.336, p.35\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy22/Z.336, p.36\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy23/Z.336, p.37\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy24/Z.336, p.38\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy25/Z.336, p.39\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 18P
.ad r
\fBFigure B\(hy26/Z.336, p.40\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 28P
.ad r
\fBFigure B\(hy27/Z.336, p.41\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy28/Z.336, p.42\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy29/Z.336, p.43\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy30/Z.336, p.44\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy31/Z.336, p.45\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 23P
.ad r
\fBFigure B\(hy32/Z.336 (feuillet 1 sur 2), p.46\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 21P
.ad r
\fBFigure B\(hy32/Z.336 (feuillet 2 sur 2), p.47\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy33/Z.336, p.48\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy34/Z.336, p.49\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy35/Z.336, p.50\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy36/Z.336, p.51\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 24P
.ad r
\fBFigure B\(hy37/Z.336, p.52\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 22P
.ad r
\fBFigure B\(hy38/Z.336, p.53\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 20P
.ad r
\fBFigure B\(hy39/Z.336, p.54\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 20P
.ad r
\fBFigure B\(hy40/Z.336, p.55\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 24P
.ad r
\fBFigure B\(hy41/Z.336, p.56\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 25P
.ad r
\fBFigure B\(hy42/Z.336, p.57\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure B\(hy43/Z.336, p.58\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 35P
.ad r
\fBFigure B\(hy44/Z.336, p.59\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 13P
.ad r
\fBFigure B\(hy45/Z.336, p.60\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp